This repository was archived by the owner on Nov 14, 2022. It is now read-only.
fix(deps): update sentry-javascript monorepo to v7.17.1 - #1642
Merged
renovate[bot] merged 1 commit intoOct 27, 2022
Conversation
renovate
Bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
October 27, 2022 19:06
6896f3e to
abaf0ca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.16.0->7.17.17.16.0->7.17.1Release Notes
getsentry/sentry-javascript
v7.17.1Compare Source
This release standardizes our SDKs to use the MIT License, which is our standard license for Sentry SDKs. We were previously using the BSD 3-Clause License in
@sentry/browser,@sentry/core,@sentry/gatsby,@sentry/hub,@sentry/integrations,@sentry/node,@sentry/react,@sentry/types,@sentry/typescript, and@sentry/utils.This release also updates the behaviour of
tracingOriginsto no longer affect span creation.tracingOriginswill only affect ifsentry-traceandbaggageheaders are attached to outgoing requests. To control span creation, use theshouldCreateSpanForRequestoption.RequestDataintegration for server-side requests (#6007)[Symbol.toStringTag]: 'Module'to CJS files (#6043)tracingOriginswhen creating spans (#6039)WINDOWfrom utils (#6024)RequestDataintegration default (#5980)RequestDataintegration in express handlers (#5990)Work in this release contributed by @philipatkinson, @Rockergmail, @ys-zhifu, and @koenpunt. Thank you for your contributions!
Special shoutout to @Tofandel who helped fix a bug in Jest that was affecting the Sentry JavaScript SDKs!
v7.17.0Compare Source
Please do not use this version - the release is broken. Upgrade to
7.17.1instead.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.